Interactive content distribution system with mobile charging device interface

ABSTRACT

An interactive content distribution system with handheld charging device and docking station. Embodiments of the present disclosure provide for an interactive content distribution system comprising a venue paging system comprising one or more handheld charging devices and docking station. In certain embodiments, the docking station serves as a communications hub between a remote server, the handheld charging devices, an administrator computing device, and one or more peripheral devices. Certain embodiments of the system may enable an administrator user to configure various systems controls of the handheld charging devices, including variable charging speed controls and geo-fencing boundaries for the handheld charging devices. In certain embodiments, a user of a mobile electronic device may be presented with digital content via the handheld charging device and/or a user application executing on the mobile electronic device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.16/870,359 filed on May 8, 2020, which claims the benefit of U.S.Provisional Application Ser. No. 62/845,709, filed on May 9, 2019, thedisclosures of each of which are hereby incorporated in their entiretyat least by reference.

FIELD

The present disclosure relates to the field of content distributionnetworks; more particularly, an interactive content distribution systemcomprising a venue paging system.

BACKGROUND

Restaurants, bars, and other entertainment venues often providedifferent types of electronic consoles on tables and/or may distributeelectronic consoles to patrons who are waiting for service. Certainprior art systems provide for consoles that include audio/visual outputdevices to provide customers with multimedia content, such as games,video and/or advertisements.

Customers may interact with the electronic consoles while visitingrestaurants, bars, and other entertainment venues that utilize suchdevices.

SUMMARY

The following presents a simplified summary of some embodiments of theinvention in order to provide a basic understanding of the invention.This summary is not an extensive overview of the invention. It is notintended to identify key/critical elements of the invention or todelineate the scope of the invention. Its sole purpose is to presentcertain exemplified embodiments of the invention in a simplified form asa prelude to the more detailed description that follows.

Certain aspects of the present disclosure provide for an interactivecontent distribution system, comprising a handheld charging devicecomprising a rechargeable battery, a charging interface configured toprovide power from the rechargeable battery to a mobile electronicdevice, a wireless communications interface, an input/output devicecomprising a visual display, and a controller comprising a processor anda non-transitory computer readable medium having processor-executableinstructions stored thereon that, when executed, cause the processor toperform one or more operations; a docking station communicably engagedwith the handheld charging device, the docking station comprising adocking interface configured to receive the handheld charging device, acharging interface configured to provide power to the rechargeablebattery of the handheld charging device, and at least one wirelessnetwork interface; and a remote server being communicably engaged withthe docking station, the remote server being configured to communicateone or more digital assets to the docking station and receive handheldcharging device activity data from the docking station; wherein the oneor more operations of the processor comprise operations for: receivingthe one or more digital assets from the docking station; presenting theone or more digital assets via the visual display; regulating a flow ofpower from the rechargeable battery to a mobile electronic device;establishing a communication interface with the mobile electronicdevice; receiving one or more user input data via the input/outputdevice in response to presenting the one or more digital assets; andproviding at least one communication to the mobile electronic device inresponse to the one or more user input data.

In accordance with certain embodiments, the interactive contentdistribution system may further comprise an administrator devicecommunicably engaged with the docking station and operable to configureone or more operations of the handheld charging device. In someembodiments, the one or more operations of the processor may compriseoperations for communicating a hyperlink or resource locator to themobile electronic device, the hyperlink or resource locator configuredto enable the mobile electronic device to install a mobile applicationassociated with the handheld charging device. The one or more operationsof the processor may further comprise operations for restricting orenabling the flow of power from the rechargeable battery to a mobileelectronic device in response to one or more user interactions with thehandheld charging device. In some embodiments, the mobile applicationmay be configured to receive at least one digital asset from thehandheld control device or the remote server. The handheld chargingdevice activity data may comprise one or more user interactions with thehandheld charging device and/or the mobile application.

In accordance with certain embodiments, the input/output device of thehandheld charging device may comprise a button or touch screen interfaceconfigured to initiate at least one communications protocol for themobile electronic device in response to a user input. In accordance withsome embodiments, the docking station may be operably configured as abroker station between the handheld charging device and the remoteserver.

Further aspects of the present disclosure provide for an interactivecontent distribution system, comprising a handheld charging devicecomprising a rechargeable battery, a charging interface configured toprovide power from the rechargeable battery to a mobile electronicdevice, a wireless communications interface, an input/output devicecomprising a visual display, and a controller configured to command oneor more operations of the handheld charging device; a docking stationcommunicably engaged with the handheld charging device, the dockingstation comprising a docking interface configured to receive thehandheld charging device, a charging interface configured to providepower to the rechargeable battery of the handheld charging device, andat least one wireless network interface; a remote server beingcommunicably engaged with the docking station via the at least onewireless network interface, the remote server being configured to sendone or more digital assets to the docking station, wherein the dockingstation is configured to send the one or more digital assets to thehandheld charging device; and an administrator device communicablyengaged with the docking station via the at least one wireless networkinterface and operable to configure one or more control settings for thehandheld charging device, the one or more control settings beingselected from the group consisting of a charging speed setting, acharging duration setting, and a content display setting, wherein thedocking station is configured as a communication hub between theadministrator device and the handheld charging device.

In accordance with certain embodiments, the handheld charging device maybe configured to restrict or enable the flow of power from therechargeable battery to the mobile electronic device in response to oneor more user interactions with the handheld charging device. Theadministrator device may be operable to configure a geofence setting forthe handheld charging device, wherein the geofence setting comprises avirtual boundary beyond which all or some functionality of the handheldcharging device is disabled. In some embodiments, the input/outputdevice of the handheld charging device further comprises a button ortouch screen interface, wherein the handheld charging device isconfigured to initiate at least one communications protocol for themobile electronic device in response to a user input via the button ortouch screen interface. In certain embodiments, the at least onecommunications protocol comprises a temporal relationship between theuser input and an output being presented on the visual display.

In certain embodiments of the interactive content distribution system,the handheld charging device may be configured to identify a knownmobile electronic device according to one or more authorizationparameters. In accordance with said embodiments, the one or moreoperations of the handheld charging device may comprise configuring oneor more content or device settings in response to the one or moreauthorization parameters.

Still further aspects of the present disclosure provide for aninteractive content distribution system, comprising a handheld chargingdevice comprising a rechargeable battery, a charging interfaceconfigured to provide power from the rechargeable battery to a mobileelectronic device, a wireless communications interface, an input/outputdevice comprising a visual display, and a controller configured tocommand one or more operations of the handheld charging device; adocking station communicably engaged with the handheld charging device,the docking station comprising a docking interface configured to receivethe handheld charging device, a charging interface configured to providepower to the rechargeable battery of the handheld charging device, andat least one wireless network interface; and a remote server configuredto provide one or more digital asset or user communication to an enduser application being native to the mobile electronic device, the enduser application being configured to authorize a charging sessionbetween the mobile electronic device and the handheld charging device.

In accordance with certain embodiments of the interactive contentdistribution system, the remote server may be communicably engaged withthe docking station via the at least one wireless network interface andconfigured to send the one or more digital asset to the docking stationfor display by the handheld charging device. The handheld chargingdevice may be configured to receive one or more user parameters from theuser application and configure one or more content settings in responseto the one or more user parameters. In some embodiments, the remoteserver may be configured to provide the one or more digital asset oruser communication to the end user application according to one or moreuser interactions with the handheld charging device. In saidembodiments, the one or more user interactions comprise at least oneuser input via the input/output device of the handheld charging device.

The foregoing has outlined rather broadly the more pertinent andimportant features of the present invention so that the detaileddescription of the invention that follows may be better understood andso that the present contribution to the art can be more fullyappreciated. Additional features of the invention will be describedhereinafter which form the subject of the claims of the invention. Itshould be appreciated by those skilled in the art that the conceptionand the disclosed specific methods and structures may be readilyutilized as a basis for modifying or designing other structures forcarrying out the same purposes of the present invention. It should berealized by those skilled in the art that such equivalent structures donot depart from the spirit and scope of the invention as set forth inthe appended claims.

BRIEF DESCRIPTION OF DRAWINGS

The skilled artisan will understand that the figures, described herein,are for illustration purposes only. It is to be understood that in someinstances various aspects of the described implementations may be shownexaggerated or enlarged to facilitate an understanding of the describedimplementations. In the drawings, like reference characters generallyrefer to like features, functionally similar and/or structurally similarelements throughout the various drawings. The drawings are notnecessarily to scale, emphasis instead being placed upon illustratingthe principles of the teachings. The drawings are not intended to limitthe scope of the present teachings in any way. The system and method maybe better understood from the following illustrative description withreference to the following drawings in which:

FIG. 1 is a block diagram of a computing device through which one ormore aspects of the present disclosure may be implemented;

FIG. 2 is an architecture diagram of a content distribution system withmobile charging interface, in accordance with an embodiment of thepresent disclosure;

FIG. 3 is a block diagram of certain network protocols for a contentdistribution system with mobile charging interface, in accordance withcertain aspects of the present disclosure;

FIG. 4 is a data flow diagram for a content distribution system withmobile charging interface, in accordance with certain aspects of thepresent disclosure;

FIGS. 5A-5D are perspective views of an exemplary handheld chargingdevice and docking station, in accordance with an embodiment of thepresent disclosure;

FIG. 6 is a functional block diagram of an exemplary docking stationbeing incorporated in a content distribution system with mobile charginginterface;

FIG. 7 is a functional block diagram of an exemplary handheld chargingdevice being incorporated in a content distribution system with mobilecharging interface;

FIG. 8 is a process flow diagram of a routine within a contentdistribution system with mobile charging interface, in accordance withcertain aspects of the present disclosure;

FIG. 9 is a process flow diagram of a routine within a contentdistribution system with mobile charging interface, in accordance withcertain aspects of the present disclosure; and

FIG. 10 is a process flow diagram of a routine within a contentdistribution system with mobile charging interface, in accordance withcertain aspects of the present disclosure.

DETAILED DESCRIPTION

It should be appreciated that all combinations of the concepts discussedin greater detail below (provided such concepts are not mutuallyinconsistent) are contemplated as being part of the inventive subjectmatter disclosed herein. It also should be appreciated that terminologyexplicitly employed herein that also may appear in any disclosureincorporated by reference should be accorded a meaning most consistentwith the particular concepts disclosed herein.

Following below are more detailed descriptions of various conceptsrelated to, and embodiments of, inventive methods, devices and systemsconfigured to provide for an interactive content distribution systemcomprising a handheld charging device with a visual display to presentdigital assets from a remote server and communicate digital assets to acommunicably engaged mobile electronic device. In certain embodiments,the handheld charging device may be configured to charge a battery of amobile electronic device via a connected charging cable. The handheldcharging device may be configured to establish a wireless or wirelinecommunications interface with the mobile electronic device to receiveand send a plurality of device communications therebetween. Inaccordance with certain aspects of the present disclosure, theinteractive content distribution system comprises a venue paging systemcomprising one or more handheld charging devices and device dockingstation. In certain embodiments the device docking station serves as acommunications hub between the remote server, the one or more handheldcharging devices, an administrator computing device, and one or moreperipheral devices. Certain embodiments of the system may enable anadministrator user to configure various systems controls of the handheldcharging devices, including variable charging speed controls andgeo-fencing boundaries. The system may also incorporate ancillaryfeature sets, including emergency notifications and other alerts. Incertain embodiments, a user of a mobile electronic device may interactwith the handheld charging device and/or the user application to viewand/or receive one or more digital assets from the handheld chargingdevice and/or the remote server. The one or more digital assets maycomprise one or more commercial advertisements.

It should be appreciated that various concepts introduced above anddiscussed in greater detail below may be implemented in any of numerousways, as the disclosed concepts are not limited to any particular mannerof implementation. Examples of specific implementations and applicationsare provided primarily for illustrative purposes. The present disclosureshould in no way be limited to the exemplary implementation andtechniques illustrated in the drawings and described below.

Where a range of values is provided, it is understood that eachintervening value, to the tenth of the unit of the lower limit unlessthe context clearly dictates otherwise, between the upper and lowerlimit of that range and any other stated or intervening value in thatstated range is encompassed by the invention. The upper and lower limitsof these smaller ranges may independently be included in the smallerranges, and are also encompassed by the invention, subject to anyspecifically excluded limit in a stated range. Where a stated rangeincludes one or both of the endpoint limits, ranges excluding either orboth of those included endpoints are also included in the scope of theinvention.

As used herein, “exemplary” means serving as an example or illustrationand does not necessarily denote ideal or best.

As used herein, the term “includes” means includes but is not limitedto, the term “including” means including but not limited to. The term“based on” means based at least in part on.

As used herein, the term “packet” refers to any formatted unit of datathat may be sent and/or received by an electronic device.

As used herein, the term “payload” refers to any part of transmitteddata that constitutes an intended message and/or identifyinginformation.

As used herein, the term “interface” refers to any shared boundaryacross which two or more separate components of a computer system mayexchange information. The exchange can be between software, computerhardware, peripheral devices, humans, and combinations thereof.

As used herein, the term “native” refers to any software program that isinstalled on a mobile electronic device.

As used herein, the term “peripheral device” refers to any internal orexternal device that connects directly to a computer but does notcontribute to the computer's primary function. In certain embodiments, aperipheral device may include any device configured to connect to acentral device over a wireless communications interface, such asBluetooth. In certain embodiments, a peripheral device may include anelectronic device configured to transmit an advertisement. In certaindevice interactions, the same device may constitute a peripheral devicein some instances and a central device in other instances.

As used herein, the term “central device” refers to any electronicdevice configured to establish a communications interface with aperipheral device. In certain embodiments, a central device may includean electronic device configured to receive an advertisement packet froma peripheral device.

As used herein, the term “master” refers to a configuration in acommunications model in which one device or process (known as themaster) controls one or more other devices or processes (known asslave(s)).

As used herein, the term “slave” refers to a configuration in acommunications model in which one or more other devices or processes(known as the slave(s)) are controlled by one or more other device orprocess (known as the master).

As used herein, the term “remote” refers to any element of a computingsystem that provides direct or indirect communication(s) to anotherelement over a communications interface, i.e. any element that functionsexternally to another element. A communications interface may include anetworked interface, such as a LAN or WAN, or may include a distributedcomputing environment in which one or more system elements maycommunicate through one or more intermediary systems and/or protocols.

As used herein, the term “handheld” refers to any form factor that is ofa size small enough to be used or operated while held in the hand orhands of a user. As used herein, the term “handheld” is not limited toform factors that are designed to be held in the hand or hands of auser, or that are actually held in the hand or hands of a user duringoperation. Rather, the term “handheld” refers to any form factor that isof a size small enough to be capable of being used or operated whileheld in the hand or hands of a user.

As used herein, the term “docking station” refers to any device that isconfigured to provide power and/or communications to one or more otherdevices. In certain embodiments, a “docking station” may be a centraldevice and the one or more other devices may comprise a peripheraldevice.

An exemplary system, method, and devices according to the principlesherein may include: 1) one or more handheld charger with an input/outputdevice including a display screen, 2) a docking station with which oneor more handheld chargers may be interfaced for charging and datatransfer, and 3) a human-machine interface configured to host formanaging a queue of patrons at a venue and sending notifications tohandheld chargers.

Certain benefits and advantages of the present disclosure over prior artvenue paging systems include providing user of a mobile electronicdevice with a means to charge the mobile electronic device (e.g.smartphone or tablet computer) while the end user waits for service atvenue and/or during the end user's patronage of the venue, and presentdigital content, such as advertisements, to the end user via a visualdisplay.

In accordance with an exemplary use case provided by embodiments of thepresent disclosure, an interactive content distribution systemcomprising a handheld charging device may be implemented in a restaurantvenue. In such an exemplary use case, the interactive contentdistribution system may be operably engaged wherein a patron of therestaurant (i.e., an end user) may approach a restaurant host (i.e., anadministrative user). If a table is not immediately ready, the host mayinput the patron's name into an administrator device (i.e. ahuman-machine interface for the system). The restaurant host may assigna handheld charger to the patron via the human-machine interface, removethe handheld charger from a docking station serving as a storagelocation for the handheld chargers, and provide one or more handheldcharger to the patron(s). Upon being assigned to the patron, thehandheld charger may begin displaying content to the patron via a visualdisplay. In certain embodiments, the content includes one or moreadvertisements and one or more device prompts configured to encouragethe patron to take one or more actions. For example, an exemplary promptmay state “5 FREE Minutes of Charge. For unlimited FREE charge, downloadthe App and pair your device.” Upon establishing a charging interfacebetween the handheld charger and the mobile electronic device, and/orupon downloading the user application and establishing a communicationinterface between the handheld charger and the mobile device, thehandheld charger may resume displaying content on the display. Theadministrative user and/or the server may configure the duration of thecharging session, and the time limit indicated on the handheld chargermay reflect the established time limit. The time limit may be latcheduntil the server pushes a time limit change to the docking station,which may be configured to write changes to the handheld controller overa communications interface.

In further accordance with the exemplary use case, upon expiration ofthe free charging period, if the patron has not paired his or her mobileelectronic device with the handheld charger, the handheld charger willdiscontinue charging the mobile electronic device and begin to vibrateand flash and/or display one or more user prompts requesting one or moreuser actions (for example, to download the user application) to continuethe charging session. Once the restaurant venue is ready to provideservice to the patron, the restaurant host may select the patron's namefrom the queue in the human-machine interface and initiating a pagingcommand to the docking station, which provides the command to thehandheld charging device to execute a paging function. In “page mode”,the handheld charger may beep, vibrate, flash and/or present a messageto the patron on the handheld charger display informing the patron toreturn to the restaurant host to receive service. Once the patronreturns the handheld charger to the restaurant host, the restaurant hostmay select the handheld charger assigned to the patron from the queue inthe human-machine interface and configure the handheld charger in atleast one secondary mode of operation. In the secondary mode ofoperation, the handheld charger may resume providing content via thevisual display and may resume charging the patron's phone. The patronmay leave the handheld charger at the table (or other location ofservice) upon exiting the restaurant. The handheld charger may then bereturned to the docking station for subsequent use.

FIGS. 1-10 are incorporated by reference in their entireties into thefollowing detailed description. Turning now descriptively to thedrawings, in which similar reference characters denote similar elementsthroughout the several views, FIG. 1 depicts a computing system in whichcertain illustrated embodiments of the present invention may beimplemented.

Referring now to FIG. 1, a processor-implemented computing device inwhich one or more aspects of the present disclosure may be implementedis shown. According to an embodiment, a processing system 100 maygenerally comprise at least one processor 102, or a processing unit orplurality of processors, memory 104, at least one input device 106 andat least one output device 108, coupled together via a bus or a group ofbuses 110. In certain embodiments, input device 106 and output device108 could be the same device. An interface 112 can also be provided forcoupling the processing system 100 to one or more peripheral devices,for example interface 112 could be a PCI card or a PC card. At least onestorage device 114 which houses at least one data storage structure 116can also be provided. The memory 104 can be any form of memory device,for example, volatile or non-volatile memory, solid state storagedevices, magnetic devices, etc. The processor 102 can comprise more thanone distinct processing device, for example to handle differentfunctions within the processing system 100. Input device 106 receivesinput data 118 and can comprise, for example, a keyboard, a pointerdevice such as a pen-like device or a mouse, audio receiving device forvoice controlled activation such as a microphone, data receiver orantenna such as a modem or a wireless data adaptor, a data acquisitioncard, etc. Input data 118 can come from different sources, for examplekeyboard instructions in conjunction with data received via a network.Output device 108 produces or generates output data 120 and cancomprise, for example, a display device or monitor in which case outputdata 120 is visual, a printer in which case output data 120 is printed,a port, such as for example a USB port, a peripheral component adaptor,a data transmitter or antenna such as a modem or wireless networkadaptor, etc. Output data 120 can be distinct and/or derived fromdifferent output devices, for example a visual display on a monitor inconjunction with data transmitted to a network. A user could view dataoutput, or an interpretation of the data output, on, for example, amonitor or using a printer. The storage device 114 can be any form ofdata or information storage means, for example, volatile or non-volatilememory, solid state storage devices, magnetic devices, etc.

In use, the processing system 100 is adapted to allow data orinformation to be stored in and/or retrieved from, via wired or wirelesscommunication means, at least one data storage structure 116. Theinterface 112 may allow wired and/or wireless communication between theprocessing unit 102 and peripheral components that may serve aspecialized purpose. In general, the processor 102 can receiveinstructions as input data 118 via input device 106 and can displayprocessed results or other output to a user by utilizing output device108. More than one input device 106 and/or output device 108 can beprovided. It should be appreciated that the processing system 100 may beany form of terminal, server, specialized hardware, or the like.

It is to be appreciated that the processing system 100 may be a part ofa networked communications system. Processing system 100 could connectto a network, for example the Internet or a WAN. Input data 118 andoutput data 120 can be communicated to other devices via the network.The transfer of information and/or data over the network can be achievedusing wired communications means or wireless communications means. Aserver can facilitate the transfer of data between the network and oneor more databases. A server and one or more database(s) provide anexample of a suitable information source.

Thus, the processing computing system environment 100 illustrated inFIG. 1 may operate in a networked environment using logical connectionsto one or more remote computers. In embodiments, the remote computer maybe a personal computer, a server, a router, a network PC, a peer device,or other common network node, and typically includes many or all of theelements described above.

It is to be further appreciated that the logical connections depicted inFIG. 1 include a local area network (LAN) and a wide area network (WAN)but may also include other networks such as a personal area network(PAN). Such networking environments are commonplace in offices,enterprise-wide computer networks, intranets, and the Internet. Forinstance, when used in a LAN networking environment, the computingsystem environment 100 is connected to the LAN through a networkinterface or adapter. When used in a WAN networking environment, thecomputing system environment typically includes a modem or other meansfor establishing communications over the WAN, such as the Internet. Themodem, which may be internal or external, may be connected to a systembus via a user input interface, or via another appropriate mechanism. Ina networked environment, program modules depicted relative to thecomputing system environment 100, or portions thereof, may be stored ina remote memory storage device. It is to be appreciated that theillustrated network connections of FIG. 1 are exemplary and other meansof establishing a communications link between multiple computers may beused.

FIG. 1 is intended to provide a brief, general description of anillustrative and/or suitable exemplary environment in which embodimentsof the invention may be implemented. That is, FIG. 1 is but an exampleof a suitable environment and is not intended to suggest any limitationsas to the structure, scope of use, or functionality of embodiments ofthe present invention exemplified therein. A particular environmentshould not be interpreted as having any dependency or requirementrelating to any one or a specific combination of components illustratedin an exemplified operating environment. For example, in certaininstances, one or more elements of an environment may be deemed notnecessary and omitted. In other instances, one or more other elementsmay be deemed necessary and added.

In the description that follows, certain embodiments may be describedwith reference to acts and symbolic representations of operations thatare performed by one or more computing devices, such as the computingsystem environment 100 of FIG. 1. As such, it will be understood thatsuch acts and operations, which are at times referred to as beingcomputer-executed, include the manipulation by the processor of thecomputer of electrical signals representing data in a structured form.This manipulation transforms data or maintains it at locations in thememory system of the computer, which reconfigures or otherwise altersthe operation of the computer in a manner that is conventionallyunderstood by those skilled in the art. The data structures in whichdata is maintained are physical locations of the memory that haveparticular properties defined by the format of the data. However, whilecertain embodiments may be described in the foregoing context, the scopeof the disclosure is not meant to be limiting thereto, as those of skillin the art will appreciate that the acts and operations describedhereinafter may also be implemented in hardware.

Embodiments may be implemented with numerous other general-purpose orspecial-purpose computing devices and computing system environments orconfigurations. Examples of well-known computing systems, environments,and configurations that may be suitable for use with embodiments of theinvention include, but are not limited to, personal computers, handheldor laptop devices, personal digital assistants, multiprocessor systems,microprocessor-based systems, set top boxes, programmable consumerelectronics, networks, minicomputers, server computers, game servercomputers, web server computers, mainframe computers, and distributedcomputing environments that include any of the above systems or devices.

Embodiments may be described in a general context of computer-executableinstructions, such as program modules, being executed by a computer.Generally, program modules include routines, programs, objects,components, data structures, etc., that perform particular tasks orimplement particular abstract data types. An embodiment may also bepracticed in a distributed computing environment where tasks areperformed by remote processing devices that are linked through acommunications network. In a distributed computing environment, programmodules may be located in both local and remote computer storage mediaincluding memory storage devices.

With the exemplary computing system environment 100 of FIG. 1 beinggenerally shown and discussed above, description will now turn towardsillustrated embodiments of the present invention which generally relateto systems, devices, and methods for an interactive content distributionsystem comprising a handheld charging device with a visual displayconfigured to present digital assets from a remote server andcommunicate digital assets to a communicably engaged mobile electronicdevice. It is to be understood and appreciated that certain aspects ofthe methods and system routines described herein comprise receiving oneor more digital content files from the docking station; presenting theone or more digital content files via the visual display; regulating aflow of power from the rechargeable battery to a mobile electronicdevice; establishing a communication interface with the mobileelectronic device; receiving one or more user input data via theinput/output device in response to presenting the one or more digitalcontent files; and communicating at least one digital content file tothe mobile electronic device in response to the one or more user inputdata.

Referring now to FIG. 2, an architecture diagram of a contentdistribution system 200 is shown. In accordance with certain aspects ofthe present disclosure, content distribution system 200 comprises adocking station 202, a handheld charger 204, an administrator device206, and a server 210. Server 210 may be communicably engaged with atleast one workstation 214 and at least one database 212. In accordancewith certain embodiments, docking station 202 may be configured toreceive one or more handheld charger 204 and provide a power interfaceto charge an internal battery of handheld charger 204. Handheld charger204 may be configured to establish a communications interface 222 and/ora power delivery interface 220 with a mobile electronic device 208 toprovide power and/or data thereto. In certain embodiments, mobileelectronic device 208 is a smart phone, tablet computer, or portablecomputing device. System 200 may further comprise, optionally, one ormore third-party system 216. Third-party system 216 may include one ormore of a restaurant point-of-sale system, a venue management system, acustomer relationship management system, and/or other businessmanagement systems related to the operation and/or management of one ormore venues. In certain embodiments, third-party system 216 iscommunicably engaged with administrator device 206 to send and receivedata therebetween.

In accordance with certain aspects of the present disclosure, dockingstation 202, handheld charger 204, mobile device 208, administratordevice 206, and (optionally) third-party system 216 may be communicablyand operably engaged within a physical location defined by a virtualboundary 218. The physical location may include a business venue, suchas a restaurant, and virtual boundary 218 may comprise a 360-degreeradius in which docking station 202 comprises a center point. In certainembodiments, virtual boundary 218 defines a maximum distance fromdocking station 202 in which handheld charger 204 may be operable. Incertain embodiments, mobile device 208 may be defined as mobile device208′ when outside of virtual boundary 218, and mobile device 208 wheninside of virtual boundary 218. When outside of virtual boundary 218,mobile device 208′ may be communicably engaged with server 210 via anInternet connection to send and receive one or more communications viaend user application 234. When inside of virtual boundary 218, mobiledevice 208 may be communicably engaged with handheld charger 204 overcommunications interface 222 and may be further communicably engagedwith handheld charger 204 via end user application 234.

In accordance with certain aspects of the present disclosure, and stillreferring to FIG. 2, content distribution system 200 may be configuredto communicate content, including delivery of one or more digitalassets, from handheld charger 204 to mobile electronic device 208. Inaccordance with an embodiment, docking station 202, handheld charger204, and administrator device 206 are operably engage within virtualboundary 218. A user of administrator device 206 may configure, viahuman-machine interface 232, a communications interface 224 betweenadministrator device 206 and docking station 202. Docking station 202may establish a communications interface 236 with handheld charger 204.Docking station 202 may establish a communications interface 228 withserver 210 via an Internet/WAN connection 230. Docking station 202 maybe configured as a communications hub to receive and send communicationsbetween server 210, handheld charger 204, and administrator device 206.In accordance with certain embodiments, human-machine interface 232 maycomprise a graphical user interface configured to enable a user ofadministrator device 206 to configure and control a plurality ofoperations/functions of handheld charger 204. In accordance with certainembodiments, human-machine interface 232 may comprise a graphical userinterface configured to enable a user of administrator device 206 to (a)manage a plurality of handheld chargers 204; (b) monitor the status of aqueue of handheld chargers 204 being assigned to one or more patrons andengaged in an operational mode; (c) select one or more handheld chargers204 for notification and/or engage one or more handheld chargers 204 ina paging mode; (d) remove handheld chargers 204 from a queue; (e) managethe queue of handheld chargers 204, including changing the order of thequeue; (f) establish a communications interface 226 with one or morethird-party system 216 to enable one or more management function, suchas monitoring the status of resource availability (e.g. tables); (g)assign handheld chargers 204 to specific customers; (h) render anddisplay an overlay of the location of each handheld charger 204 on agraphical map; (i) configure one or more parameters for virtual boundary218; (j) add/remove handheld chargers 204 and docking stations 202 froma device registry; (k) display a charge level of each handheld charger204 in a device registry; (l) configure a charging speed for handheldcharger 204 (e.g., a “Restaurant Mode” (105% of normal speed) and a “BarMode” (90% of normal speed)); (m) engage one or more handheld chargers204 into alarm mode; (n) configure a time limit for a charging sessionbetween handheld charger 204 and mobile electronic device 208; (o)configure and provide one or more static assets to handheld charger 204,such as a digital file of a restaurant menu; and (p) establishcommunications interface 228, communications interface 224,communications interface 236, and communications interface 226.

In accordance with certain aspects of the present disclosure,administrator device 206, docking station 202, handheld charger 204, andserver 210 are operably engaged to provide digital content to a user ofmobile device 208. In certain embodiments, the digital content comprisesa commercial advertisement. The digital content may further comprise oneor more interactive games and/or creative content, such as movies,television shows, and/or music. Workstation 214 may be communicablyengaged with server 210 to configure one or more digital assets 238comprising the digital content and provide the digital assets 238 toserver 210. Server 210 may store the digital assets 238 in database 212.Server 210 may communicate digital assets 238 to docking station 202 anddocking station 202 may communicate digital assets 238 to handheldcharger 204, which may store digital assets 238 in local memory.Administrator device 206 may configure one or more controls/logic viahuman-machine interface 232 to cause handheld charger 204 to renderdigital assets 238 and present the digital content via an integrateddisplay device, which may be provisioned to handheld charger 204 bydocking station 202 via communications interface 236. Human-machineinterface 232 may be configured to enable a user of administrator device206 to initiate a first mode of operation for handheld charger 204. Uponinitiating a first mode of operation, handheld charger 204 may beconfigured to render digital assets 238 and display content on thedisplay device. Handheld charger 204 may be configured to prompt theuser of mobile electronic device 208 to establish communicationsinterface 222 and/or power transfer interface 220 between mobileelectronic device 208 and handheld charger 204. Handheld charger 204 maybe configured to determine whether the user of mobile electronic device208 is a known user of system 200 by determining, for example, whethermobile electronic device 208 has end user application 234 installedthereon. In certain embodiments, end user application 234 is a nativemobile application installed on the operating system of mobileelectronic device 208. End user application 234 may also comprise ahybrid mobile application or a Web application that is executed via amobile browser. Handheld charger 204 may be configured to selectivelyenable/disable power transfer interface 220, and/or configure one ormore power transfer permissions, in response to the one or more userinteractions. Handheld charger 204 may communicate device data,including device usage data and user interaction data, to dockingstation 202. Docking station 202 may communicate the device data toserver 210 and/or administrator device 206. Server 210 may store thedevice data in database 212 and may further configure and/or selectdigital assets 238 in accordance with the device data. Server 210 mayprovide one or more push communications to mobile electronic device 208′in accordance with the device data, including one or more digital assets238. Handheld charger 204 may be configured to provide digital assets238 to mobile electronic device 208 in response to one or more userinteractions between handheld charger 204 and/or mobile electronicdevice 208. In accordance with various aspects of the presentdisclosure, handheld charger 204 may be configured to provide digitalassets 238 to mobile electronic device 208 in accordance with one ormore communications protocols. In certain embodiments, handheld charger204 may be configured to provide a communication to mobile electronicdevice 208 comprising a data packet containing a resource identifier orother data structure configured to facilitate and/or authorize mobileelectronic device 208 to retrieve one or more digital assets 238 fromserver 210. In other embodiments, handheld charger 204 may be configuredto communicate user interaction data and/or device activity data todocking station 202. Docking station 202 may communicate the userinteraction data and/or device activity data to server 210, and server210 may provide one or more digital assets 238 to mobile electronicdevice 208. In certain embodiments, digital assets 238 may include anoptical code (for example, a QR code) that is presented concurrentlywith other content being presented on the visual display of handheldcharger 204 (for example, the optical code may be embedded or overlaidwith other digital content be presented on the visual display). In suchembodiments, mobile electronic device 208, and/or one or more ancillarymobile electronic devices, may be configured to scan the optical code inorder to retrieve one or more of digital assets 238 from server 210.

Referring now to FIG. 3 (with references to FIG. 2), a block diagram ofnetwork protocols within a content distribution system 300 is shown. Inaccordance with certain aspects of the present disclosure, contentdistribution system 300 may be comprised of a server 310, dockingstation master 302 and optionally one or more docking station slaves 302a-n, an administrator device 304, one or more handheld chargers 306 a-n,and one or more mobile electronic devices 302 a-n. In accordance withcertain aspects of the present disclosure content distribution system300 may be embodied as content distribution system 200 (as shown in FIG.2), wherein server 310 may comprise server 210, docking station master302 and docking station slaves 302 a-n may each comprise docking station202, administrator device 304 may comprise administrator device 206,handheld chargers 306 a-n may each comprise handheld charger 204, andmobile electronic devices 302 a-n may each comprise mobile electronicdevice 208.

In accordance with certain aspects of the present disclosure, system 300may comprise a plurality of network protocols comprising a plurality ofrules, procedures and formats to define communication between server310, docking station master 302, one or more docking station slaves 302a-n, an administrator device 304, one or more handheld chargers 306 a-n,and one or more mobile electronic devices 302 a-n. In certainembodiments, docking station master 302 is configured as a centraldevice and one or more docking station slaves 302 a-n are configured asperipheral devices. Docking station master 302 may be configured toestablish a network interface 314 with one or more docking stationslaves 302 a-n in which docking station master 302 is established as amaster device and docking station slaves 302 a-n are slave devices in anetwork communication protocol. In accordance with an embodiment,network interface 314 may comprise a BLUETOOTH protocol. In accordancewith an embodiment, docking station master 302 may be configured as abroker station for communication between handheld chargers 306 a-n andadministrator device 304 and/or server 310.

Docking station master 302 and docking station slaves 302 a-n may becommunicably engaged with handheld chargers 306 a-n via networkinterface 312. In certain embodiments, network interface 312 maycomprise a radio frequency protocol comprising one or more sub-gigahertzradio frequency bands to enable lower power consumption and long-rangetransmissions. In certain embodiments, network interface 312 maycomprise a LORA protocol. In some embodiments, handheld chargers 306 a-nmay be configured to send one or more communications to docking stationmaster 302 and/or docking station slaves 302 a-n via network interface312 to determine whether handheld chargers 306 a-n have exceeded avirtual boundary (i.e., a threshold distance from docking station master302 and/or docking station slaves 302 a-n). In some embodiments, networkinterface 312 may further comprise at least one tunneling protocol 318through which communications from handheld chargers 306 a-n and dockingstation slaves 302 a-n may be repackaged and sent by docking stationmaster 302 to server 310 via Internet/WAN 308. Tunneling protocol 318may be further operable to encapsulate one or more communications overnetwork interface 312 to enable a data transfer interface betweennetwork interface 312 and Internet/WAN 308, in which docking stationmaster 302 is a broker station.

In certain embodiments, administrator device 304 may be communicablyengaged with docking station master 302 via network interface 316.Network interface 314 may comprise a BLUETOOTH protocol. Networkinterface 314 may be operably engaged with tunneling protocol 318 toestablish a communications interface with Internet/WAN 308, in whichdocking station master 302 is a broker station between administratordevice 304 and server 310. In other embodiments, administrator device304 may be communicably engaged with server 310 via a WIFI connection322. In certain embodiments, administrator device 304 may be configuredas a central device and docking station master 302 may be configured asa peripheral device, and vice versa. In accordance with certainembodiments, network interface 316 may comprise certain protocols inwhich docking station master 302 is configured as a master device andadministrator device 304 is configured as a slave device; and mayfurther comprise certain protocols in which docking station master 302is configured as a slave device and administrator device 304 may beconfigured as a master device. In accordance with certain aspects of thepresent disclosure, handheld chargers 306 a-n may be communicablyengaged with mobile electronic devices 302 a-n via network interface320. In certain embodiments, network interface 320 may be configured asa BLUETOOTH protocol or a WIFI protocol. Handheld chargers 306 a-n maybe configured to receive one or more network communications containingone or more data packets from docking station master 302 via networkinterface 312 and may be configured to send one or more networkcommunications containing the one or more data packets from handheldchargers 306 a-n to docking station master 302 via network interface312. In accordance with certain embodiments, the one or more datapackets may comprise a digital content file. In accordance with certainembodiments, network interface 320 may comprise certain protocols inwhich handheld chargers 306 a-n is/are configured as a master device andmobile electronic devices 302 a-n is/are configured as a slave device;and may further comprise certain protocols in which handheld chargers306 a-n is/are configured as a slave device and mobile electronicdevices 302 a-n is/are configured as a master device. In certainembodiments, mobile electronic devices 302 a-n may communicate one ormore user-generated data and/or device activity data to handheldchargers 306 a-n via network interface 320. Handheld chargers 306 a-nmay communicate the one or more user-generated data and/or deviceactivity data to docking station master 302 and/or docking stationslaves 302 a-n via network interface 312. Docking station master 302 maycommunicate the one or more user-generated data and/or device activitydata to administrator device 304 via network interface 316; and dockingstation master 302 may communicate the one or more user-generated dataand/or device activity data to server 310 via network interface 322.

Referring now to FIG. 4, a flow diagram of a data flow schema 400 for acontent distribution system is shown. In accordance with certain aspectsof the present disclosure, data flow schema 400 may be implemented inaccordance with the network protocols of system 300, as shown in FIG. 3.Data flow schema 400 may define a data flow between one or more elementswithin system 200, as shown in FIG. 2; for example, server 210,administrator device 206, docking station 202, handheld charger 204 andmobile electronic device 208. In accordance with certain aspects of thepresent disclosure, data flow schema 400 is configured to defineprovisioning and control data 402 at administrator device 206.Provisioning and control data 402 may be communicated from administratordevice 206 to docking station 202, and communicated from docking station202 to handheld charger 204. Provisioning and control data 402 may bestored in local memory of handheld charger 204. Provisioning and controldata 402 may comprise network provisioning data to establish networkprotocols between the administrator device 206, docking station 202, andhandheld charger 204. Provisioning and control data 402 may alsocomprise control data to configure one or more operations of handheldcharger 204 including, but not limited to, geofence settings, contentdisplay controls, charging speed, charging session duration, andconfiguring one or more operational modes such as a paging mode.

In accordance with certain aspects of the present disclosure, data flowschema 400 is configured to define a plurality of digital assets 404 atserver 210. One or more digital assets 404 may be communicated fromserver 210 to docking station 202, and communicated from docking station202 to handheld charger 204. One or more digital assets 404 may bestored in local memory of handheld charger 204. One or more digitalassets 404 may comprise one or more static or dynamic digital contentfiles. In an embodiment, digital assets 404 comprise digital contentcomprising a commercial advertisement. Digital assets 404 may furthercomprise one or more dynamic content files, such interactive games.Digital assets 404 may comprise multiple file formats such as image fileformats, video file formats, and/or audio file formats.

In accordance with aspects of the present disclosure, handheld charger204 may initiate a charging session with mobile electronic device 208.In certain embodiments, mobile electronic device 208 may generate userdata 408 during the charging session, and handheld charger 204 maygenerate device data 406 during the charging session. User data 408 maycomprise user-generated data such as user inputs into a mobileapplication and may further comprise static user data, such asuser/device identification data. Device data 406 may include deviceactivity data, such as device inputs (e.g., button presses), duration ofcharging session, duration of display of digital assets, timing andidentification of display of digital assets, and temporal data fordevice inputs, charging initiation/duration, and display of digitalassets. Handheld charger 204 may receive user data 408 from mobileelectronic device 208 and communicate user data 408 and device data 406to docking station 202. Docking station 202 may receive user data 408and device data 406 and communicate user data 408 and device data 406 toserver 210. Server 210 may receive user data 408 and device data 406 andstore user data 408 and device data 406 in a database.

In accordance with aspects of the present disclosure, handheld charger204 may communicate one or more digital assets 404 to mobile electronicdevice 208 in response to receiving/processing user data 408 and/ordevice data 406. In accordance with certain embodiments, handheldcharger 204 communicate one or more digital assets 404 to mobileelectronic device 208 in response to receiving a device input whiledisplaying content on a display device. In certain embodiments, handheldcharger 204 may communicate the digital asset 404 to mobile electronicdevice 208 according to a temporal relationship between the device inputand the content being displayed on the display device. In certainembodiments, mobile electronic device 208 receives digital asset 404 andstores it in local memory. In other embodiments, mobile electronicdevice 208 receives digital asset 404 via a mobile application, throughwhich digital asset 404 is stored in a remote server and accessible tomobile electronic device 208 via the mobile application. In accordancewith certain aspects of the present disclosure, mobile application data412 may be generated in response to one or more user interactions withthe mobile application; for example, accessing digital asset 404. Mobileelectronic device 208 may be configured to communicate mobileapplication data 412 to server 210. Server 210 may be configured toreceive and process mobile application data 412 according to serverlogic 416. Server logic 416 may be configured to select, modify and/orconfigure additional digital assets 404 to be distributed to dockingstation 202 and handheld charger 204 in response to mobile applicationdata 412. In certain embodiments, server 210 may be configured toreceive and process user data 408 and device data 406 according toserver logic 416. Server logic 416 may be further configured to select,modify and/or configure additional digital assets 404 to be distributedto docking station 202 and handheld charger 204 in response to user data408 and device data 406.

Referring now to FIGS. 5A-5D, perspective views of an exemplary handheldcharger 500 and docking station 510 are shown. In accordance withcertain aspects of the present disclosure, handheld charger 500 maycomprise an exemplary embodiment of handheld charger 204 of system 200,as shown in FIG. 2. Docking station 510 may comprise an exemplaryembodiment of docking station 202 of system 200, as shown in FIG. 2. Incertain embodiments, handheld charger 500 may be comprised of a housinghaving a form factor being configured to be held in a hand or hands of auser during use. Handheld charger 500 may be comprise of a displayscreen 502, a lighting output 504, and an input device 506. Handheldcharger 500 may comprise a housing constructed from plastic and may beassembled such that an interior portion of the housing is waterproofwhen submerged in water. Display screen 502 may comprise an LED displayand may be configured to display images and/or videos. Lighting output504 may comprise one or more LEDs, or other light sources, and beconfigured to pulse, flash and/or modulate a duty cycle of the one ormore LEDs according to one or more operational settings. Input device506 may comprise a button disposed on a surface of the housing ofhandheld charger 500. Input device 506 may engage a sensor and/or acircuit, when pressed by a user, to send a signal to an internalprocessor of input device 506. Handheld charger 500 may comprise one ormore device charging cables 508 a-c. In an embodiment, charging cable508 a may be configured as a USB-C charging cable; charging cable 508 bmay be configured as a Micro USB charging cord; and charging cable 508 cmay be configured as a LIGHTNING charging cord. Charging cables 508 a-cmay enable a power transfer interface between an internal battery ofhandheld charger 500 and an internal charger of a mobile electronicdevice, such as a smart phone or tablet computer. According to anembodiment, docking station 510 is configured to receive one or morehandheld chargers 500 a-n at one or more charger ports 514. One or morecharger ports 514 may be configured as a complementary shape to handheldchargers 500 a-n such that handheld chargers 500 a-n may be interfacedwith charger ports 514 for storage and recharging. Charger ports 514 mayfurther comprise a power transfer interface 512 configured to provide aflow of power from docking station 510 to an internal charger ofhandheld charger 500. Power transfer interface 512 may comprise one ormore contact terminals configured to establish a connection with one ormore contact terminals of handheld charger 500. Alternatively, powertransfer interface 512 may comprise an inductive charging interface toenable a wireless transmission of power between docking station 510 andhandheld charger 500.

Referring now to FIG. 6, a functional block diagram of an exemplarydocking station 600 is shown. In accordance with certain aspects of thepresent disclosure, docking station 600 (and docking station slave 628)may comprise an exemplary embodiment of docking station 202 of system200 (as shown in FIG. 2). In accordance with certain aspects of thepresent disclosure, server 624 may comprise an exemplary embodiment ofserver 210 (as shown in FIG. 2); administrator device 626 may comprisean exemplary embodiment of administrator device 206 (as shown in FIG.2); and handheld charger 630 may comprise an exemplary embodiment ofhandheld charger 204 (as shown in FIG. 2). In accordance with anembodiment, docking station 600 may comprise a housing 601 beingconfigured to define an external surface and an interior portion inwhich one or more electronic components of docking station 600 may behoused. Docking station 600 may comprise a form factor such as that ofdocking station 510, as shown in FIG. 5. Docking station 600 maycomprise a controller 602 configured to enable a plurality of operationsof docking station 600. Controller 602 may be comprised of a processor604, a non-transitory memory device 606, and a wireless communicationchipset 608. In accordance with certain embodiments, wirelesscommunication chipset 608 may include a BLUETOOTH chipset 610, a WIFIchipset 612, and a LORA chipset 614. In accordance with certainembodiments, BLUETOOTH chipset 610, a WIFI chipset 612, and a LORAchipset 614 may be incorporated into a single integrated chipset.Controller 602 may be operably engaged with a power supply 622 viasystem bus 640 to receive a flow of power from a power source. Incertain embodiments, power supply 622 may be housed within housing 601and configured to draw less than or equal to 4.5 amps at 120V AC or 2.25amps at 240V AC. Power supply 622 may comprise a connector configured tointerface with a power outlet; for example, a standard NEMA 5-15Rconnector. Docking station 600 may further comprise a fan, heatsink, orother thermal sink to prevent overheating of one or more electroniccomponents. Memory device 606 may comprise one or moreprocessor-executable instructions stored thereon to command processor604 to perform one or more operations. In an embodiment, memory device606 may have an internal data storage capacity sufficient to store aplurality of digital assets comprising up to 10 minutes of digital videohaving a resolution of not less than one megapixel, a color depth of notless than 16-bit, and a refresh rate of not less than 30 Hz, plus 100%overhead minimum.

Docking station 600 may further comprise a charger dock 616 beingoperably engaged with controller 602 via system bus 640. Charger dock616 may comprise one or more charger ports 618 a-n being disposed on asurface of housing 601 and configured to receive and store one or morehandheld chargers 630. Charger ports 618 a-n may comprise one or morecontact terminals operably engaged with system bus 640 to provide apower transfer interface between charger ports 618 a-n and the one ormore handheld chargers. Charger ports 618 a-n may be configured suchthat a handheld charger 630 may be operably interfaced with the one ormore contact terminals upon being placed into one of charger ports 618a-n. The one or more contact terminals may be waterproof orwater-resistant. In certain embodiments, charger dock 616 is configuredto fully recharge a depleted handheld controller in less than 20minutes. In an exemplary embodiment, charger dock 616 is configured toreceive and charge up to eight handheld controllers simultaneously.

In certain embodiments, docking station 600 may further comprise one ormore LEDs 620 disposed on a surface of housing 601 and operably engagedwith controller 602 via system bus 640. In accordance with certainaspects of the present disclosure, controller 602 may be configured toestablish a communications interface 632 with a remote server 624. Incertain embodiments, WIFI chipset 612 is configured to establish a WIFIconnection to enable communications interface 632. Controller 602 may befurther configured to establish a communications interface 634 withadministrator device 626. In certain embodiments, BLUETOOTH chipset 610is configured to establish a BLUETOOTH connection between wirelesschipset 608 and administrator device 626 to enable communicationsinterface 632. Controller 602 may be further configured to establish acommunications interface 638 with a slave docking station 628. Incertain embodiments, BLUETOOTH chipset 610 is configured to establish aBLUETOOTH connection between wireless chipset 608 and slave dockingstation 628 to enable communications interface 632. Controller 602 maybe further configured to establish a communications interface 636 withat least one handheld charger 630. In certain embodiments, LORA chipset614 is configured to establish a low-power radio frequency communicationinterface (e.g. LORA) between wireless chipset 608 and handheld charger630 to enable communications interface 632. In certain embodiments,docking station 600 is configured to serve as a broker station betweenadministrator device 626 and handheld controllers 630, in accordancewith one or more network protocols. In certain embodiments, dockingstation 600 is configured to serve as a broker station between server624 and handheld controllers 630, in accordance with one or more networkprotocols.

In accordance with certain embodiments, processor 604, memory device 606and wireless communication chipset 608 may be operably engaged toexecute one or more network protocols to receive and send one or moredata packets to and from administrator device 626, and receive and sendone or more data packets to and from handheld controller 630. Memorydevice 606 may comprise one of more processor-executable instruction tocause processor 604 to process a payload of the one or more data packetsand perform one or more operations for provisioning handheld controllers630, assigning handheld controllers 630 to a device roster, registeringbutton-press events from handheld controllers 630, determining a signalstrength of handheld controllers 630, and other operations to ensureoverall system requirements are met. Processor 604, memory device 606and wireless communication chipset 608 may be operably engaged toestablish and control one or more geofence settings. Handheld controller630 may communicate with controller 602 via communications interface 636to determine whether handheld controller 630 has exceeded a virtualboundary defined by the one or more geofence settings. Processor 604,memory device 606 and wireless communication chipset 608 may be operablyengaged to execute one or more network protocols to receive and send oneor more data packets to and from administrator device 626 and/or server624 to receive over-the-air firmware and software updates viacommunications interface 634 and/or communications interface 632. Incertain embodiments, controller 602 may send a request to handheldcharger 630 via communications interface 636 at designated timeintervals (e.g. five seconds) to determine a charge status and signalstrength of handheld charger 630. Controller 602 may communicate thecharge status and signal strength of handheld charger 630 toadministrator device 626 via communications interface 634. In accordancewith certain embodiments, controller 602 may be configured to commandthe highest-charged handheld charger 630 to flash a lighting output upona request from administrator device 626 to assign a new handheld charger630 to a customer. In accordance with certain embodiments, controller602 may be communicably engaged with each handheld controller 630 thatis docked in one or more charger ports 618 a-n. Controller 602 andhandheld controller 630 may be communicably engaged via one or moredigital or serial communication means, including via one or more RX/TXpins. Controller 602 and handheld charger 630 may be communicablyengaged to execute one or more data transfer protocols, including butnot limited to: loading digital assets onto handheld controller 608;updating firmware on handheld controller 608; and downloading devicedata from handheld controller 608 (for example, content display data,device interaction data, temporal data comprising timing of deviceinteractions and content display, battery charge level over time) todocking station 600. Controller 602 may be configured to package devicedata downloaded from handheld controller 608 and communicate the devicedata to server 624 via communications interface 632 and/or administratordevice 262 via communications interface 634.

Referring now to FIG. 7, a functional block diagram of an exemplaryhandheld charger 700 is shown. In accordance with certain aspects of thepresent disclosure, handheld charger 700 may comprise handheld charger630 (as shown in FIG. 6) and/or may comprise handheld charger 204 ofsystem 200 (as shown in FIG. 2). In accordance with certain aspects ofthe present disclosure, docking station master 732 and docking stationslave 734 may each be configured as docking station 600 (as shown inFIG. 6) and/or docking station 202 of system 200 (as shown in FIG. 2).Administrator device 748 may comprise administrator device 626 (as shownin FIG. 6) and/or may comprise administrator device 206 of system 200(as shown in FIG. 2). Mobile electronic device 736 may be configured asany commercial-off-the-shelf mobile electronic device, such as a smartphone or tablet computer, and may be configured as mobile electronicdevice 208 of system 200 (as shown in FIG. 2). In accordance with anembodiment, handheld charger 700 may comprise a housing 701 beingconfigured to define an external surface and an interior portion inwhich one or more electronic components of handheld charger 700 may behoused. Handheld charger 700 may comprise a form factor such as that ofhandheld charger 500, as shown in FIG. 5. In accordance with certainembodiments, handheld charger 700 may comprise a controller 702comprising a wireless communication chipset 704, a processor 710, and anon-transitory computer readable memory device 712. Memory device 712may comprise one or more processor-executable instructions storedthereon to command processor 710 to perform one or more operations. Inan embodiment, memory device 712 may have an internal data storagecapacity sufficient to store a plurality of digital assets comprising upto 10 minutes of digital video having a resolution of not less than onemegapixel, a color depth of not less than 16-bit, and a refresh rate ofnot less than 30 Hz, plus 100% overhead minimum. Memory 712 may beconfigured to have an internal data storage capacity sufficient to storea plurality of digital assets comprising up to 50 video advertisementshaving a resolution of not less than one megapixel, a color depth of notless than 16-bit, and a refresh rate of not less than 30 Hz, plus 100%overhead minimum. Controller 702 may be operably engaged with a display728 to render and output a visual output comprising one or more digitalcontent files, and a speaker 724 to render and output an audio outputcomprising one or more digital content files. Controller 702 may beoperably engaged with display 728 and speaker 724 via a system bus 744.In an embodiment, display 728 may comprise an LED or LCD display havinga resolution of not less than one megapixel, a color depth of not lessthan 16-bit, and a refresh rate of not less than 30 Hz.

In accordance with certain embodiments, handheld charger 700 may furthercomprise an optical sensor 746 communicably engaged with controller 702and configured to scan a machine-readable optical code (such as a QRcode). Handheld charger 700 may further comprise a lighting device 730comprising one or more LEDs. Lighting device 730 may be communicablyengaged with controller 702 to generate a light output in response toone or more command signals from controller 702. In accordance withcertain embodiments, controller 702 may be communicably engaged withlighting device 730 to illuminate a proportional to the number of LEDsto indicate a charge level of battery 714 (for example, if battery 714is at a 50% charge, controller 702 may cause lighting device 730 toilluminate 50% of the number of LEDs and/or luminous output). Handheldcharger 700 may further comprise a vibrating motor 722 communicablyengaged with controller 702 and configured to generate a vibrational(e.g., haptic) output in response to one or more command signals fromcontroller 702. Handheld charger 700 may further comprise a fan,heatsink, or other thermal sink to prevent overheating of one or moreelectronic components. Handheld charger 700 may further comprise abattery 714 being configured to store a charge of power and providepower to controller 702, and all other electronic elements of handheldcharger 700, via system bus 744. Battery 714 may be operably engagedwith a battery charger 720 to receive power from a power source andprovide a charge to battery 714. In accordance with certain embodiments,battery charger 720 and battery 714 may be operably configured toestablish a power transfer interface with docketing station master 732and/or docking station slave 734 and be operable to recharge battery 714from 0% to 100% in less than 20 minutes. Handheld charger 700 mayfurther comprise a charging interface 716 comprising one or morecharging cables 718 a-n. In an embodiment, a charging cable 718 a may beconfigured as a USB-C charging cable; charging cable 718 b may beconfigured as a Micro USB charging cable; and charging cable 508 c maybe configured as a LIGHTNING charging cable. Charging cables 508 a-c mayenable a power transfer interface between battery 714 and an internalcharger of mobile electronic device 736. In an embodiment, charginginterface 716 may be operably engaged with battery 714 to charge mobileelectronic device 736 from 0% to 75% in less than 40 minutes (assumingmobile electronic device 736 is capable of accepting such a chargerate). In certain embodiments, battery 714 may have a power storagecapacity in the range of about 1000 milliamp hours to about 10,000milliamp hours. However, it is anticipated that battery 714 may have apower storage capacity above or below this range in accordance withcertain exemplary embodiments and commercial use cases.

In accordance with certain embodiments, handheld charger 700 may beconfigured to establish a wireless communications interface 738 betweencontroller 702 and docking station master 732 to send and receive one ormore communications from administrator device 748 via docking stationmaster 732. In accordance with certain embodiments, administrator device748 may be configured to send one or more command signals to controller702 via docking station master 732. Controller 702 may be configured toprocess, with processor 710, the one or more command signals to causehandheld charger 700 to perform one or more operations and/or initiateone or more modes of operation. For example, administrator device 748may be configured to send a command signal configured to causecontroller 702 to execute a mode of operation comprising a “Page Mode.”In accordance with an embodiment, upon initiating a Page Mode controller702 is operable to engage an output from vibrating motor 722, speaker724, and lighting output 730, and display 728 is configured to alert auser of handheld charger 700 to take a specified action (e.g., returnhandheld charger 700 to a specified location within a venue). Inaccordance with certain embodiments, controller 702 may be operablyengaged with optical sensor 746 to scan a machine-readable optical code(e.g. a QR code) being presented on a display of mobile electronicdevice 736. Controller 702 may be operable to process a data packetreceived by the machine-readable optical code and establish acommunications interface 740 between handheld charger 700 and mobileelectronic device 736. Alternatively, handheld charger 700 may beconfigured to present a machine-readable optical code via display 728.Mobile electronic device 736 may be configured to scan themachine-readable optical code and process a data packet received by themachine-readable optical code to establish communications interface 740between handheld charger 700 and mobile electronic device 736.Alternatively, handheld charger 700 may be configured to present analphanumeric code via display 728. A user of mobile electronic device736 may input the alphanumeric code via a graphical user interface of auser application to establish communications interface 740 betweenhandheld charger 700 and mobile electronic device 736.

In accordance with certain embodiments, handheld charger 700 may becommunicably engaged with docking station master 732 and/or dockingstation slave 734 via communications interface 738 to receive aplurality of data packets comprising digital assets, software and/orother device data, and store the data in memory 712 (as constrained by adata storage limit for memory 712). Handheld charger 700 may becommunicably engaged with docking station master 732 and/or dockingstation slave 734 via communications interface 738 to provide locationdata for handheld charger 700 in order to determine whether handheldcharger 700 is inside or outside of a virtual boundary of a geofencesetting. In accordance with certain embodiments, handheld charger 700may be configured to execute an alternative mode of operation uponexceeding the boundary of the geofence setting (e.g. a “Suicide Mode”).In accordance with an embodiment, upon executing a “Suicide Mode,”controller 702 is configured to command a continuous output from speaker724 and vibrate until handheld charger 700 returns to within theboundary of the geofence setting and re-establishes communicationinterface 738 with the docking station master 732 or docking stationslave 734. In certain embodiments, handheld charger 700 may beconfigured to re-establish communication interface 738 with the dockingstation master 732 or docking station slave 734 upon being interfacedwith charger dock 616 of docking station 600 (as shown in FIG. 6). Ifhandheld charger 700 is not returned, handheld charger 700 may continueto broadcast a charge status and location until battery 714 is depleted.In certain embodiments, upon executing a “Suicide Mode,” controller 702is configured to disable or restrict some or all functions of handheldcharger 700. For example, in certain embodiments controller 702 may beconfigured to disable the power transfer interface between battery 714and mobile electronic device 736. Controller 702 may be furtherconfigured to disable the presentation of content via display 728 and/orpresent one or more user notifications or messages via display 728(e.g., a message prompting the user to return handheld charger 700 to adesignated location or area).

Handheld controller 700 may be communicably engaged with administratordevice 748 via communications interface 738 with docking station master732 to receive and process one or more data packets related to one ormore system commands, functions and/or operational requirements.Controller 702 may receive and process the one or more data packets, andprocessor 710 may execute one or more operations in response to the oneor more data packets. In certain embodiments, the one or more operationsmay comprise operations for provisioning handheld controller 700,assigning handheld controller 700 to a device roster, registering inputsfrom input device 726, determining a signal strength handheld controller700, and other operations to ensure overall system requirements are met.Handheld controller 700 may be communicably engaged with docking stationmaster 732 to receive and process, via controller 702, over-the-airfirmware and software updates.

Referring now to FIG. 8, a process flow diagram of a routine 800 withina content distribution system is shown. Routine 800 may be implementedwithin content distribution system 200, as shown in FIG. 2. Inaccordance with certain aspects of the present disclosure, routine 800may comprise provisioning a plurality of network protocols within acontent distribution system (for example, content distribution system200, as shown in FIG. 2). In accordance with an embodiment, routine 800may be initiated by establishing a communications interface between anadministrator device and a docking station (step 802). Routine 800 mayoptionally comprise establishing a communications interface between anadministrator device and one or more third-party systems (step 814).Routine 800 may continue by establishing a communications interfacebetween the docking station and a remote server (step 804). Routine 800may continue by establishing a communications interface between thedocking station and one or more handheld chargers (step 806). Routine800 may optionally comprise establishing a communications interfacebetween a master docking station and one or more slave docking stations(step 816). Routine 800 may continue by provisioning and/or configuringone or more control settings of the one or more handheld chargers (step808). Step 808 may comprise routing a communication comprising theprovisioning and/or control data from the administrator device to thedocking station, and from the docking station to the one or morehandheld chargers. Routine 800 may continue by providing one or moredigital assets to the one or more handheld chargers (step 810). Step 810may comprise routing a communication comprising the one or more digitalassets from the remote server to the docking station, and from thedocking station to the one or more handheld chargers. Routine 800 mayconclude by configuring one or more status and/or settings for the oneor more handheld chargers in a human-machine interface executing on theadministrator device. (step 812). Step 810 may comprise routing acommunication comprising the one or more operational or system data fromthe administrator device to the docking station, and from the dockingstation to the one or more handheld chargers.

Referring now to FIG. 9, a process flow diagram of a routine 900 withina content distribution system is shown. Routine 900 may be implementedwithin content distribution system 200, as shown in FIG. 2. Inaccordance with certain aspects of the present disclosure, routine 900may comprise a continuation of routine 800 and/or subroutine of routine800 (as shown in FIG. 8). Routine 900 may be executed successively orconcomitantly from routine 800 and/or may be executed independent ofroutine 800 (as shown in FIG. 8). In accordance with certain embodimentsof the present disclosure, routine 900 may be initiated by assigning ahandheld charger to a position in a queue of handheld chargers within ahuman-machine interface executing on an administrator device (step 902).Step 902 may comprise providing a communication configured to assign thehandheld charger to a queue position from the administrator device tothe docking station, and from the docking station to the handheldcharger. Routine 900 may continue by initiating, with the handheldcharger, an operational mode comprising a charging and content displaysession (step 904). Routine 900 may continue by displaying, via adisplay device of the handheld charger, audio/video content comprisingone or more commercial advertisements and one or more user promptsconfigured to prompt a view to initiate a charging session between thehandheld charger and a mobile electronic device (step 908). If the userdoes not initiate a charging session between the handheld charger andthe mobile electronic device, either within a specified time period orin response to a user input, routine 900 continues by restricting and/ordisabling one or more display or power functions of the handheld charger(step 920). If the user initiates a charging session between thehandheld charger and the mobile electronic device, routine 900 continueswith a decision step 910 to determine whether the mobile electronicdevice contains a user application for the handheld charger and/orwhether the user has a user account for the user application. If YES,routine 900 continues by presenting digital content via the display ofthe handheld charger and enabling one or more power transfer interfacebetween the handheld charger and the mobile electronic device (step912). If NO, routine 900 continues by presenting a user prompt, via thedisplay of the handheld charger, configured to prompt the user toinstall or configure the user application (step 918). If the user doesnot install the user application for the handheld charger on the mobileelectronic device and/or does not configure a user account for the userapplication, either within a specified time period or in response to auser input, routine 900 continues by restricting and/or disabling one ormore display or power functions of the handheld charger (step 920).(Routine 900 may continue from step 920 to step 922, as describedbelow.) If the user does install the user application for the handheldcharger on the mobile electronic device and/or configures a user accountfor the user application, routine 900 continues by presenting digitalcontent via the display device of the handheld charger and enabling oneor more power transfer interface between the handheld charger and themobile electronic device (step 912). Routine 900 may continue byreceiving a user input, via an input device on the handheld charger, inresponse to digital content being displayed on the display device of thehandheld charger (step 914). Routine 900 may continue by communicating,via a wireless communications interface, a digital content file from thehandheld charger to the mobile electronic device in response to the userinput (step 914). In certain embodiments, step 914 further comprisesdetermining a temporal relationship between the user input and a timelocation within the digital content file. Step 914 may be furtherconfigured to select a digital content file according to the temporalrelationship between the user input and a time location within thedigital content file.

In accordance with certain embodiments, routine 900 may continue bysending a paging communication from the administrator device to thedocking station, and from the docking station to the handheld charger(step 922). Upon receiving the paging communication, the handheldcharger may execute a Paging Mode comprising one or more pagingfunctions (step 924). Routine 900 may continue by terminating thecharging session for the handheld controller and updating the devicequeue, via the human-machine interface of the administrator device, toreturn the handheld controller to an available status within the devicequeue (step 926). In certain embodiments, step 926 may compriseterminating the charging session for the handheld controller via thehuman-machine interface of the administrator device and/or terminatingthe charging session for the handheld controller automatically inresponse to the expiration of a predetermined time period or uponestablishing an interface between the handheld charger and the dockingstation. In certain embodiments, routine 900 may comprise determiningwhether a geofence boundary has been exceeded in response to a locationcommunication from the handheld controller to the docking station (step930). If the geofence boundary has been exceeded, routine 900 mayterminate the charging session in accordance with step 926 and/or mayexecute one or more mode of operation or functionality of the handheldcharger. Routine 900 may conclude by communicating charging session datafrom the handheld charger to the docking station, and from the dockingstation to the server and/or the administrator device (step 928). Incertain embodiments, step 928 may be executed in response toestablishing a charging interface between the handheld charger and thedocking station.

Referring now to FIG. 10, a process flow diagram of a routine 1000within a content distribution system is shown. Routine 1000 may beimplemented within content distribution system 200, as shown in FIG. 2.In accordance with certain aspects of the present disclosure, routine1000 may comprise a continuation of routine 800 and/or subroutine ofroutine 800 (as shown in FIG. 8); and/or routine 1000 may comprise acontinuation of routine 900 and/or subroutine of routine 900 (as shownin FIG. 8). Routine 1000 may be executed successively or concomitantlywith routine 800 and/or may be executed independent of routine 800 (asshown in FIG. 8); and/or routine 1000 may be executed successively orconcomitantly with routine 900 and/or may be executed independent ofroutine 900 (as shown in FIG. 9). In accordance with certain embodimentsof the present disclosure, routine 1000 may (optionally) be initiated bypushing a communication from a remote server to a mobile electronicdevice having an associated user application installed (step 1002). Inaccordance with certain embodiments, step 1002 may further comprisepushing a communication from the server to the user application topromote one or more specific service locations associated with thecontent distribution system (step 1008). In accordance with certainembodiments, routine 1000 may continue from step 1002 by initiating asession of the user application on the mobile electronic device (step1004). Routine 1000 may continue by collecting user-generated dataand/or user interactions associated with the session of the userapplication (step 1006). Routine 1000 may continue by communicating theuser data and/or interactions from the mobile electronic device to theserver (step 1010). In accordance with certain instances of routine1000, routine 1000 may conclude at step 1010. Alternatively, step 1006may further comprise collecting user data and/or interactions from themobile electronic device wherein the user visits a service location andthe content distribution system is operably engaged (step 1012). Routine1000 may continue by establishing, with the mobile electronic device, acommunications interface between the mobile electronic device and ahandheld charger being located at the service location and initiating acharging session between the handheld charger and the mobile electronicdevice (step 1014). Routine 1000 may continue by communicating devicedata to the server, wherein the device data comprises session data forthe mobile electronic device (step 1016). In an embodiment, step 1016may comprise communicating device data from the handheld charger to thedocking station, and from the docking station to the server. Routine1000 may continue by providing and/or configuring one or more digitalassets in response to the device data (step 1018). Step 1016 may beexecuted at the handheld charger and may comprise providing content thatis relevant or configured for the user in response to the user data. Forexample, the content may be selected based on one or more userpreferences or user interaction, such as displaying a videoadvertisement for a brand in which the user has previously indicated aninterest. Step 1016 may further comprise configuring one or more digitalassets at the server and communicating the one or more digital assetsfrom the server to the docking station, and from the docking station tothe handheld controller. The one or more digital assets may comprise oneor more offers or rewards based on one or more user preferences and/oruser interactions. For example, the server may configure a digital assetcomprising a coupon for use at the service location based on the one ormore user preferences and/or user interactions, e.g. a coupon for anitem that the user has previously purchased. Routine 1000 may continueby terminating the session between the handheld charger and the mobileelectronic device in response to a command by the administrator deviceand/or in response to terminating the communications interface betweenthe mobile electronic device and the handheld charger (step 1022).Routine 1000 may conclude by communicating charging session data fromthe handheld charger to the docking station, and from the dockingstation to the server and/or the administrator device (step 1024). Incertain embodiments, step 1024 may be executed in response toestablishing a charging interface between the handheld charger and thedocking station.

As will be appreciated by one of skill in the art, the present inventionmay be embodied as a method (including, for example, acomputer-implemented process, a business process, and/or any otherprocess), apparatus (including, for example, a system, machine, device,computer program product, and/or the like), or a combination of theforegoing. Accordingly, embodiments of the present invention may takethe form of an entirely hardware embodiment, an entirely softwareembodiment (including firmware, resident software, micro-code, etc.), oran embodiment combining software and hardware aspects that may generallybe referred to herein as a “system.” Furthermore, embodiments of thepresent invention may take the form of a computer program product on acomputer-readable medium having computer-executable program codeembodied in the medium.

Any suitable transitory or non-transitory computer readable medium maybe utilized. The computer readable medium may be, for example but notlimited to, an electronic, magnetic, optical, electromagnetic, infrared,or semiconductor system, apparatus, or device. More specific examples ofthe computer readable medium include, but are not limited to, thefollowing: an electrical connection having one or more wires; a tangiblestorage medium such as a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), a compact discread-only memory (CD-ROM), or other optical or magnetic storage device.

In the context of this document, a computer readable medium may be anymedium that can contain, store, communicate, or transport the programfor use by or in connection with the instruction execution system,apparatus, or device. The computer usable program code may betransmitted using any appropriate medium, including but not limited tothe Internet, wireline, optical fiber cable, radio frequency (RF)signals, or other mediums.

Computer-executable program code for carrying out operations ofembodiments of the present invention may be written in an objectoriented, scripted or unscripted programming language such as Java,Perl, Smalltalk, C++, or the like. However, the computer program codefor carrying out operations of embodiments of the present invention mayalso be written in conventional procedural programming languages, suchas the “C” programming language or similar programming languages.

Embodiments of the present invention are described above with referenceto flowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products. It will be understood thateach block of the flowchart illustrations and/or block diagrams, and/orcombinations of blocks in the flowchart illustrations and/or blockdiagrams, can be implemented by computer-executable program codeportions. These computer-executable program code portions may beprovided to a processor of a general purpose computer, special purposecomputer, or other programmable data processing apparatus to produce aparticular machine, such that the code portions, which execute via theprocessor of the computer or other programmable data processingapparatus, create mechanisms for implementing the functions/actsspecified in the flowchart and/or block diagram block or blocks.

These computer-executable program code portions (i.e.,computer-executable instructions) may also be stored in acomputer-readable memory that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the code portions stored in the computer readablememory produce an article of manufacture including instructionmechanisms which implement the function/act specified in the flowchartand/or block diagram block(s). Computer-executable instructions may bein many forms, such as program modules, executed by one or morecomputers or other devices. Generally, program modules include routines,programs, objects, components, data structures, etc. that performparticular tasks or implement particular abstract data types. Typically,the functionality of the program modules may be combined or distributedas desired in various embodiments.

The computer-executable program code may also be loaded onto a computeror other programmable data processing apparatus to cause a series ofoperational phases to be performed on the computer or other programmableapparatus to produce a computer-implemented process such that the codeportions which execute on the computer or other programmable apparatusprovide phases for implementing the functions/acts specified in theflowchart and/or block diagram block(s). Alternatively, computer programimplemented phases or acts may be combined with operator or humanimplemented phases or acts in order to carry out an embodiment of theinvention.

As the phrases are used herein, a processor may be “operable to” or“configured to” perform a certain function in a variety of ways,including, for example, by having one or more general-purpose circuitsperform the function by executing particular computer-executable programcode embodied in computer-readable medium, and/or by having one or moreapplication-specific circuits perform the function.

The terms “program” or “software” are used herein in a generic sense torefer to any type of computer code or set of computer-executableinstructions that can be employed to program a computer or otherprocessor to implement various aspects of the present technology asdiscussed above. Additionally, it should be appreciated that accordingto one aspect of this embodiment, one or more computer programs thatwhen executed perform methods of the present technology need not resideon a single computer or processor, but may be distributed in a modularfashion amongst a number of different computers or processors toimplement various aspects of the present technology.

All definitions, as defined and used herein, should be understood tocontrol over dictionary definitions, definitions in documentsincorporated by reference, and/or ordinary meanings of the definedterms.

The indefinite articles “a” and “an,” as used herein in thespecification and in the claims, unless clearly indicated to thecontrary, should be understood to mean “at least one.” As used herein,the terms “right,” “left,” “top,” “bottom,” “upper,” “lower,” “inner”and “outer” designate directions in the drawings to which reference ismade.

The phrase “and/or,” as used herein in the specification and in theclaims, should be understood to mean “either or both” of the elements soconjoined, i.e., elements that are conjunctively present in some casesand disjunctively present in other cases. Multiple elements listed with“and/or” should be construed in the same fashion, i.e., “one or more” ofthe elements so conjoined. Other elements may optionally be presentother than the elements specifically identified by the “and/or” clause,whether related or unrelated to those elements specifically identified.Thus, as a non-limiting example, a reference to “A and/or B”, when usedin conjunction with open-ended language such as “comprising” can refer,in one embodiment, to A only (optionally including elements other thanB); in another embodiment, to B only (optionally including elementsother than A); in yet another embodiment, to both A and B (optionallyincluding other elements); etc.

As used herein in the specification and in the claims, “or” should beunderstood to have the same meaning as “and/or” as defined above. Forexample, when separating items in a list, “or” or “and/or” shall beinterpreted as being inclusive, i.e., the inclusion of at least one, butalso including more than one, of a number or list of elements, and,optionally, additional unlisted items. Only terms clearly indicated tothe contrary, such as “only one of” or “exactly one of,” or, when usedin the claims, “consisting of,” will refer to the inclusion of exactlyone element of a number or list of elements. In general, the term “or”as used herein shall only be interpreted as indicating exclusivealternatives (i.e. “one or the other but not both”) when preceded byterms of exclusivity, such as “either,” “one of,” “only one of,” or“exactly one of.” “Consisting essentially of,” when used in the claims,shall have its ordinary meaning as used in the field of patent law.

As used herein in the specification and in the claims, the phrase “atleast one,” in reference to a list of one or more elements, should beunderstood to mean at least one element selected from any one or more ofthe elements in the list of elements, but not necessarily including atleast one of each and every element specifically listed within the listof elements and not excluding any combinations of elements in the listof elements. This definition also allows that elements may optionally bepresent other than the elements specifically identified within the listof elements to which the phrase “at least one” refers, whether relatedor unrelated to those elements specifically identified. Thus, as anon-limiting example, “at least one of A and B” (or, equivalently, “atleast one of A or B,” or, equivalently “at least one of A and/or B”) canrefer, in one embodiment, to at least one, optionally including morethan one, A, with no B present (and optionally including elements otherthan B); in another embodiment, to at least one, optionally includingmore than one, B, with no A present (and optionally including elementsother than A); in yet another embodiment, to at least one, optionallyincluding more than one, A, and at least one, optionally including morethan one, B (and optionally including other elements); etc.

In the claims, as well as in the specification above, all transitionalphrases such as “comprising,” “including,” “carrying,” “having,”“containing,” “involving,” “holding,” “composed of,” and the like are tobe understood to be open-ended, i.e., to mean including but not limitedto. Only the transitional phrases “consisting of” and “consistingessentially of” shall be closed or semi-closed transitional phrases,respectively, as set forth in the United States Patent Office Manual ofPatent Examining Procedures, Section 2111.03.

The present disclosure includes that contained in the appended claims aswell as that of the foregoing description. Although this invention hasbeen described in its exemplary forms with a certain degree ofparticularity, it is understood that the present disclosure of has beenmade only by way of example and numerous changes in the details ofconstruction and combination and arrangement of parts may be employedwithout departing from the spirit and scope of the invention. Therefore,it will be apparent to those skilled in the art that variousmodifications and variations can be made to the disclosed embodimentswithout departing from the scope or spirit of the invention. In view ofthe foregoing, it is intended that the invention covers modificationsand variations of this disclosure within the scope of the followingclaims and their equivalents.

What is claimed is:
 1. An interactive content distribution system,comprising: a handheld charging device comprising a rechargeablebattery, a charging interface configured to provide power from therechargeable battery to a mobile electronic device, a wirelesscommunications interface, an input/output device comprising a visualdisplay, and a controller comprising a processor and a non-transitorycomputer readable medium having processor-executable instructions storedthereon that, when executed, cause the processor to perform one or moreoperations; a docking station communicably engaged with the handheldcharging device, the docking station comprising a docking interfaceconfigured to receive the handheld charging device, a charging interfaceconfigured to provide power to the rechargeable battery of the handheldcharging device, and at least one wireless network interface; and aremote server being communicably engaged with the docking station, theremote server being configured to communicate one or more digital assetsto the docking station and receive handheld charging device activitydata from the docking station; wherein the one or more operations of theprocessor comprise operations for: receiving the one or more digitalassets from the docking station; presenting the one or more digitalassets via the visual display; regulating a flow of power from therechargeable battery to a mobile electronic device; establishing acommunication interface with the mobile electronic device; receiving oneor more user input data via the input/output device in response topresenting the one or more digital assets; and providing at least onecommunication to the mobile electronic device in response to the one ormore user input data.
 2. The system of claim 1 further comprising anadministrator device communicably engaged with the docking station andoperable to configure one or more operations of the handheld chargingdevice.
 3. The system of claim 1 wherein the one or more operations ofthe processor comprise operations for communicating a hyperlink orresource locator to the mobile electronic device, the hyperlink orresource locator configured to enable the mobile electronic device toinstall a mobile application associated with the handheld chargingdevice.
 4. The system of claim 1 wherein the input/output device of thehandheld charging device further comprises a button or touch screeninterface configured to initiate at least one communications protocolfor the mobile electronic device in response to a user input.
 5. Thesystem of claim 1 wherein the docking station is operably configured asa broker station between the handheld charging device and the remoteserver.
 6. The system of claim 1 wherein the one or more operations ofthe processor further comprise operations for restricting or enablingthe flow of power from the rechargeable battery to the mobile electronicdevice in response to one or more user interactions with the handheldcharging device.
 7. The system of claim 3 wherein the mobile applicationis configured to receive the one or more digital assets from thehandheld control device or the remote server.
 8. The system of claim 3wherein the handheld charging device activity data comprises one or moreuser interactions with the handheld charging device and/or the mobileapplication.
 9. An interactive content distribution system, comprising:a handheld charging device comprising a rechargeable battery, a charginginterface configured to provide power from the rechargeable battery to amobile electronic device, a wireless communications interface, aninput/output device comprising a visual display, and a controllerconfigured to command one or more operations of the handheld chargingdevice; a docking station communicably engaged with the handheldcharging device via the wireless communications interface, the dockingstation comprising a docking interface configured to receive thehandheld charging device, a charging interface configured to providepower to the rechargeable battery of the handheld charging device, andat least one wireless network interface; a remote server beingcommunicably engaged with the docking station, the remote server beingconfigured to send one or more digital assets to the docking station,wherein the docking station is configured to send the one or moredigital assets to the handheld charging device; and an administratordevice communicably engaged with the docking station via the at leastone wireless network interface and operable to configure one or morecontrol settings for the handheld charging device, the one or morecontrol settings being selected from the group consisting of a chargingspeed setting, a charging duration setting, and a content displaysetting, wherein the docking station is configured as a communicationhub between the administrator device and the handheld charging device.10. The system of claim 9 wherein the handheld charging device isconfigured to restrict or enable the flow of power from the rechargeablebattery to the mobile electronic device in response to one or more userinteractions with the handheld charging device.
 11. The system of claim9 wherein the administrator device is operable to configure a geofencesetting for the handheld charging device, wherein the geofence settingcomprise a virtual boundary beyond which all or some functionality ofthe handheld charging device is disabled.
 12. The system of claim 9wherein the input/output device of the handheld charging device furthercomprises a button or touch screen interface, wherein the handheldcharging device is configured to initiate at least one communicationsprotocol for the mobile electronic device in response to a user inputvia the button or touch screen interface.
 13. The system of claim 12wherein the communications protocol is configured according to atemporal relationship between the user input and an output beingpresented on the visual display.
 14. The system of claim 9 wherein thehandheld charging device is configured to identify a known mobileelectronic device according to one or more authorization parameters. 15.The system of claim 14 wherein the one or more operations of thehandheld charging device comprise configuring one or more content ordevice settings in response to the one or more authorization parameters.16. An interactive content distribution system, comprising: a handheldcharging device comprising a rechargeable battery, a charging interfaceconfigured to provide power from the rechargeable battery to a mobileelectronic device, a wireless communications interface, an input/outputdevice comprising a visual display, and a controller configured tocommand one or more operations of the handheld charging device; adocking station communicably engaged with the handheld charging device,the docking station comprising a docking interface configured to receivethe handheld charging device, a charging interface configured to providepower to the rechargeable battery of the handheld charging device, andat least one wireless network interface; and a remote server configuredto provide one or more digital assets or user communication to an enduser application being native to the mobile electronic device, the enduser application being configured to authorize a charging sessionbetween the mobile electronic device and the handheld charging device.17. The system of claim 16 wherein the remote server is communicablyengaged with the docking station via the at least one wireless networkinterface and configured to send the one or more digital assets to thedocking station for display by the handheld charging device.
 18. Thesystem of claim 17 wherein the handheld charging device is configured toreceive one or more user parameters from the user application andconfigure one or more content settings in response to the one or moreuser parameters.
 19. The system of claim 16 wherein the remote server isconfigured to provide a digital asset or user communication to the enduser application according to one or more user interactions with thehandheld charging device.
 20. The system of claim 19 wherein the one ormore user interactions comprise at least one user input via theinput/output device of the handheld charging device.